|
A software metric is a standard of measure of a degree to which a software system or process possesses some property. Even if a metric is not a measurement (metrics are functions, while measurements are the numbers obtained by the application of metrics), often the two terms are used as synonymous. Since quantitative measurements are essential in all sciences, there is a continuous effort by computer science practitioners and theoreticians to bring similar approaches to software development. The goal is obtaining objective, reproducible and quantifiable measurements, which may have numerous valuable applications in schedule and budget planning, cost estimation, quality assurance testing, software debugging, software performance optimization, and optimal personnel task assignments. == Common software measurements == Common software measurements include: * Balanced scorecard * Bugs per line of code * Code coverage * Cohesion * Comment density〔(【引用サイトリンク】url=http://www.lsec.dnd.ca/qsd_current_version/eng_support/di/metrics.htm )〕 * Connascent software components * Coupling * Cyclomatic complexity (McCabe's complexity) * DSQI (design structure quality index) * Function Points and Automated Function Points, an Object Management Group standard * Halstead Complexity * Instruction path length * Maintainability index * Number of classes and interfaces * Number of lines of code * Number of lines of customer requirements * Program execution time * Program load time * Program size (binary) * Robert Cecil Martin's software package metrics * Weighted Micro Function Points * CISQ automated quality characteristics measures 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Software metric」の詳細全文を読む スポンサード リンク
|